question to team, do we want to use useKeyboard for this, it stops events by default so we MUST call continuePropagation here for the "Escape" key to clear the selection.

This is not ideal because it causes the event to continue by default instead through all other event handlers. See my thoughts on this in the description of #8775

This is not ideal because it causes the event to continue by default instead through all other event handlers.

Hm, maybe I’m remembering something wrong but isn't that only an issue because the handlers further up do not consistently useKeyboard themselves?

If that were the case propagation wouldnt flow upwards uncontrollably, since it would be stopped at every level if not explicitly continued.

That's a good point, I might've been thinking about it wrong. Looking at https://github.com/adobe/react-spectrum/blob/main/packages/%40react-aria/interactions/src/createEventHandler.ts which would be called each time useKeyboard is used it looks like the previous continue would be overwritten and stop would be called.

I still do not like that users would need to know all the keys they should continue for the ListBox to work though. So I'm still not sure about using useKeyboard here.

I'm not sure why a user wouldn't just call continue for any key, besides the ones with explicit purpose in his custom event handler. The same should be done in our parent handler, aka continue on everything we don't explicitly want to stop for. It basically translates to the exact thing you proposed in #8775, where there is an explicit intent of I do not want collisions to this key attached to any stop and yet we do not continue uncontrollably because we still need to think about calling continue explicitly every time we add a new handler.

I guess you could still argue that the user would have to know there is some keyboard interactivity that he may break if he doesn't continue in his handler, but I figure that would be discovered rather quickly.